Additional documents of interest
- Successful Business Continuity - Part 1 - Users and Groups
-
This article was published in the April 2005 issue of
AIX Update magazine
and discusses system administration needs and requirements oriented
around users and groups. The overall emphasis of this series of
articles is for implementation of enterprise wide unique identifiers
for a variety of parameters, such as user names, group names, UID and
GID numbers.
- Successful Business Continuity - Part 2 - Machine and Host Names
-
This article was published in the May 2005 issue of
AIX Update magazine
and discusses naming structures for machines, systems, adapters, and
aliases. The overall emphasis of this series of articles is for
implementation of enterprise wide unique identifiers for a variety of
parameters.
- Successful Business Continuity - Part 3 - Volume Names
-
This article was published in the December 2005 issue of
AIX Update magazine
and discusses naming structures for volume groups, logical volumes, log
logical volumes, directory mount points, etc. The overall emphasis of
this series of articles is for implementation of enterprise wide unique
identifiers for a variety of parameters.
- Successful Business Continuity - Part 4 - MQ Series, Startup/Shutdown Scripts, Error Processing
-
This article was published in the April 2006 issue of
AIX Update magazine
and discusses how to implement AIX in an environment dedicated to
business continuity. The topic of this article is the assignment of MQ
Series queue names and aliases, resource group startup and shutdown
script names (Application startup/shutdown script names), error logging,
and error notification.
- Successful Business Continuity - Part 5 - Miscellaneous topics
-
This article was published in the August 2006 issue of
AIX Update magazine
and discusses how to implement AIX in an environment dedicated to
business continuity. A variety of topics is discussed in this article
including automated documentation generation and management.
- Automated Microcode Management System
-
One of the most difficult administration tasks in an AIX environment is
attempting to keep the firmware and microcode up-to-date. Mt Xia has
devised an automated method of gathering the Microcode information,
determining which microcode needs to be updated, generating reports, and
uploading the required microcode updates to each individual system.
- Calculating the size of a Virtual Processor
-
This document describes the algorithms used to calculate the size of a
virtual processor when using shared processors in an LPAR. The IBM
documentation describes how to calculate CPU utilization, NOT how to
size for configuration, this document clarifies this process. A
description of the HMC input fields for the processor tab is included.
- Basics of Partition Load Manager Setup
-
This presentation was provided by Ron Barker from IBM regarding the PLM Basic
setup.
- ppt
- pdf
|
 |
 |
 |
 |
This document references the standards implemented by Mt Xia to ensure
business continuity for all business functions implemented on the AIX
Power 5 architecture. Many of these standards are not specific to the
Power5 architecture but are intended as enterprise wide standards for
all AIX systems.
These standards have been developed over many years of supporting
standalone, high availability, and disaster recovery environments. The
purpose of these standards is to ensure business continuity during
normal system maintenance, planned and unplanned outages, hardware and
software failures, network and communication failures, and/or a disaster
recovery implementation.
A design aspect of these standards is they can be implemented in a
standalone, high availability, or disaster recovery scenario. Recognize
that there are not multiple standards, one for each scenario, there is
one single standard that is portable across all scenario's. This
reduces support and training costs, and increases efficiency,
supportability, recoverability, and availability.
Some of the basic concepts of these standards:
- Business functions are not tied to a specific machine.
- Hardware resources can be shared or distributed among
associated business functions.
- Any system can act as a failover for any other system.
- Any data center can act as a disaster recovery site for any
other data center.
|
 |
 |
 |
 |
|
|
